home *** CD-ROM | disk | FTP | other *** search
I have been using PC-NFS with Mosaic for about 6 to 8 months. I don't have any real problems with it unless you include no DNS as a problem. I simply took the mosaic.ini file and filtered out all the standard distribution http and ftp system names and then wrote a script to run them throughnslookup to get their addresses. I do get an occasional GPF, and maybe that could be related to the resource leak talked about in another article. Anyway...What I really want to know is if anyone has seen a patch to PC-NFS to allow it to do DNS? If Sun plans to put DNS in the next version, I hope they put out a patch for the rest of us! In article <1994Mar9.194431.14851@ultb.isc.rit.edu>, epp4010@ultb.isc.rit.edu (E.P. Pylko) says: > >In article <HARRY.94Mar8085249@abu.mgh.harvard.edu> harry@abu.mgh.harvard.edu (Harry Hochheiser) writes: >> >>I'm looking for the latest and greatest Winsock.dll for PC-NFS 5.0. >>Any suggestions? I've got a Winsock, dated 3/2/93, but I'm having >>trouble running Mosaic, and I suspect winsock.dll may be at fault. >>Anybody out there have any similar problems? > >It's probably because PC-NFS 5.0 doesn't have/use DNS. Version 5.1 >(which I hear is due out this month) is supposed to support DNS. > >-Eric > >>-------------- >>Harry Hochheiser >>Department of Biomedical Engineering >>Massachusetts General Hospital >>(617)726-6881 >>harry@dbe.mgh.harvard.edu >-- >Eric Pylko Great minds talk about ideas. >epp4010@ultb.isc.rit.edu Average minds talk about things. >epp4010@cs.rit.edu Simple minds talk about people. From news@bigblue.oit.unc.edu Thu Mar 10 19:43:15 1994 Received: from bigblue.oit.unc.edu by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP id AA06947; Thu, 10 Mar 1994 19:58:27 -0500 Received: by bigblue.oit.unc.edu (AIX 3.2/UCB 5.64/4.03) id AA09816; Thu, 10 Mar 1994 19:45:09 -0500 Received: from GATEWAY by bigblue with netnews for winsock@sunsite.unc.edu (winsock@sunsite.unc.edu) To: winsock@sunsite.unc.edu Date: Thu, 10 Mar 1994 19:43:15 GMT From: stevem@hpdml90.boi.hp.com (Steve Messinger) Message-Id: <CMGs45.90y@boi.hp.com> Organization: Hewlett-Packard / Boise, Idaho Sender: ses References: <mark.smith%ccmail.3.000A27C1@x400gw.msfc.nasa.gov> Subject: Re: nfs client for winsock? mark smith (mark.smith%ccmail@x400gw.msfc.nasa.gov) wrote: : I am not sure whether it is possible or not, but I would like to see if there : are any winsock compliant nfs client packages out there. All of the resources : I have found so far require the nfs client to run at dos time. : Thanks, : Mark Smith : mark.smith%ccmail@x400gw.msfc.nasa.gov This was posted a few days ago in comp.protocols.tcp-ip.ibmpc: From: ddl@harvard.edu (Dan Lanciani) Newsgroups: comp.protocols.tcp-ip.ibmpc Subject: free DOS/Windows NFS client available Message-ID: <249@ddlgw.UUCP> Date: 25 Feb 94 02:47:07 GMT Organization: Internet Lines: 10 I have placed a version of my nfs client in pub/nfs on hsdndev.harvard.edu for anonymous ftp. This incarnation supports the MS/3Com/HP/WfWG TSR stack and, as such, is somewhat constrained by the small maximum send sizes of that socket interface. Otherwise, it should be quite usable. For more details, refer to the manual file in the above directory. Dan Lanciani ddl@harvard.* -- Steve Messinger Hewlett-Packard, Boise ID stevem@hpdml90.boi.hp.com From news@bigblue.oit.unc.edu Fri Mar 11 00:36:05 1994 Received: from bigblue.oit.unc.edu by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP id AA06958; Thu, 10 Mar 1994 19:58:29 -0500 Received: by bigblue.oit.unc.edu (AIX 3.2/UCB 5.64/4.03) id AA21852; Thu, 10 Mar 1994 19:50:46 -0500 Received: from GATEWAY by bigblue with netnews for winsock@sunsite.unc.edu (winsock@sunsite.unc.edu) To: winsock@sunsite.unc.edu Date: 11 Mar 1994 00:36:05 GMT From: support@wrq.com Message-Id: <2loedl$s7i@news.u.washington.edu> Organization: Walker, Richer & Quinn Sender: ses Reply-To: support@wrq.com Subject: Sockets, Winsock, and Reflection Socket Support (FAQ) Last-modified: 1994/03/09 Version: 1.0 FREQUENTLY ASKED QUESTIONS ABOUT SOCKETS AND REFLECTION SOCKET SUPPORT This posting has been prepared by Walker Richer & Quinn, Inc. (WRQ) to answer commonly asked questions about sockets, Windows Sockets, and socket support in WRQ's Reflection products. This information is current as of March 1994 and subject to change. What questions does this answer? 1. What are "sockets"? 2. What are "TCP Sockets"? 3. What is the "Windows Sockets" API? 4. Can I use my application with Reflection Network Series? 5. Can Reflection for DOS terminal emulators use my TCP/IP software? 6. Can Reflection for Windows emulators use my TCP/IP software? 7. Can Reflection X use my TCP/IP stack? 8. Can Reflection FTP for Windows use my TCP/IP stack? 9. Can NS/VT (VT-MGR connections) run over a WINSOCK.DLL? 10. How do all these network modules fit together? If you have any related questions or comments, please contact WRQ at <support@wrq.com> or other means listed at the end of this posting. 1. WHAT ARE "SOCKETS"? "Sockets" is the name for an Application Program Interface (API). APIs allow communication between programs. Socket-based applications typically run over TCP/IP networks. The model for sockets began at Berkeley in the 1980s with UNIX (BSD 4.2). Sockets were ported to PCs for communication between applications and networking software. As PCs proliferated, manufacturers of TCP/IP software implemented socket interfaces differently. There are different DOS-based sockets (TSRs) and different Windows-based sockets (DLLs). 2. WHAT ARE "TCP SOCKETS"? The TCP Sockets interface supports applications written to socket libraries from HP, 3Com, Microsoft, and DEC (PATHWORKS TCP/IP prior to 5.0). This interface is also commonly known as "HP ARPA Sockets" and "Microsoft TCP/IP Sockets". TCP Sockets are supported in Reflection Network Series for DOS 2.01 and later. WRQ's program that supplies this functionality is WRQHPSO.EXE. Some Windows applications may also use WSOCKETS.DLL or the older WIN_SOCK.DLL. (Note: These are not the same as WINSOCK.DLL and are not Windows Sockets compliant.) Examples of applications that use TCP Sockets: - PC X Window System servers such as Reflection X, AGE Xoftware, Hummingbird HCL-eXceed/W, and Vision Ware XVision - Database front ends such as Oracle SQL*Net, Sybase OpenClient, and HP AllBase. - PC e-mail packages such as HP OpenMail and HP New Wave Mail To develop an application that uses TCP Sockets, you need to obtain a development kit from Microsoft. Call any LAN Manager Authorized Dealer and ask for Part #0962744-005. 3. WHAT IS THE "WINDOWS SOCKETS" API? This is a new sockets standard for Microsoft Windows applications. A consortium of more than 20 software and hardware vendors created the Windows Sockets API known as "Winsock". Windows Sockets specification version 1.1 was completed and published on January 20, 1993. If a Windows application is written to the Windows Sockets API, it is designed to run on any Windows Sockets TCP/IP stack. This means the Windows application is "Windows Sockets compatible" and is a "Windows Sockets application". In order to work with Windows Sockets applications, PC TCP/IP vendors must write their own version of a WINSOCK.DLL file that will work with their stack and follow the Windows Sockets API. The underlying TCP/IP can be DOS-based TSR programs, Windows-based DLLs, or a mixture of the two. Many PC TCP/IP vendors provide a WINSOCK.DLL for their stack (listed below). This makes their TCP/IP network software "Windows Sockets compliant". Common problems with WINSOCK.DLL files: a. You must use the WINSOCK.DLL file that is provided by your TCP/IP vendor. Since each WINSOCK.DLL is written for a specific TCP/IP stack, these files are not interchangeable. b. To use Windows Sockets, the file must be named WINSOCK.DLL (no underscore). The files WIN_SOCK.DLL and WSOCKETS.DLL are for the HP Sockets specification (see 2. above) and will not work as Windows Sockets. Do not rename these files; unpredictable results will occur. c. The WINSOCK.DLL file typically needs to be in your Windows directory, or somewhere in your DOS search path. Otherwise, it will not be found by your Windows Sockets application. d. You should have only one Windows Sockets compliant TCP/IP stack on each PC. If there are multiple WINSOCK.DLL files, unpredictable results can occur. e. Even though Windows Sockets is a standard, the specification is still open to interpretation and variations among TCP/IP vendors. In some cases, these differences can cause compatibility problems between the application and the TCP/IP stack. You many need to contact the manufacturer for a software update, such as a different WINSOCK.DLL version. Some Windows Sockets compliant TCP/IP stacks: Beame & Whiteside BW-NFS, version 3.0C Digital PATHWORKS TCP/IP, version 5.0 * Distinct TCP/IP, version 3.00 Frontier Technologies Corp. Super-TCP for Windows, version 3.00 FTP Software PC/TCP, version 2.2 and later * IBM TCP/IP for DOS, version 2.1 IBM TCP/IP for OS/2 with DOS/Windows Access Kit, version 2.0 Microsoft TCP/IP, version 1.0 * Microsoft Windows NT TCP/IP NetManage Chamelon, version 3.10 and later * Novell LAN WorkPlace for DOS, version 4.1 Sun Microsystems PC-NFS, version 5.00 Wollongong Pathway Access, version 2.1.1 WRQ Reflection Network Series for DOS (TCP Connection, 3000 Connection, NS Connection), version 2.2 ** WRQ Reflection Network Series for Windows (TCP Connection or 3000 Connection) *** * see e. above. ** As of March 1994, Reflection Network Series for DOS 2.11 is the current shipping product. A free 2.2 upgrade will be available to 2.1x customers who need Windows Sockets compliance. The WINSOCK.DLL provided in version 2.2 will run over the RNS DOS-based TSRs. Beta version is scheduled to be available in April 1994. *** Reflection Network Series for Windows is a new product family that will primarily use Windows-based DLLs (instead of DOS-based TSRs) for the network modules. The WINSOCK.DLL will run over the other RNS DLLs. Beta version is scheduled to be available in April 1994. More information on the Windows Sockets specification is available from the anonymous FTP site sunsite.unc.edu (152.2.22.81) in the directory /pub/micro/pc-stuff/ms-windows/winsock. 4. CAN I USE MY APPLICATION WITH REFLECTION NETWORK SERIES? WRQ's TCP/IP software is available in the Reflection Network Series (RNS) TCP Connection, 3000 Connection, or NS Connection. The following socket interfaces and other interfaces are supported: TCP Sockets Supported in Reflection Network Series for DOS 2.01 and later. This supports many applications written to the HP ARPA, Microsoft, and DEC PATHWORKS socket libraries. (See 2. above.) Windows Sockets Reflection Network Series for DOS 2.2 will be Windows Sockets compliant (beta available in April 1994). Reflection Network Series for Windows 4.0 will also be Windows Sockets compliant when released (beta available in April 1994). The WINSOCK.DLL we provide will support Windows Sockets compatible applications. (See also 3. above.) NetIPC/TICL Supported in Reflection Network Series for DOS 2.01 and later. NetIPC is an API used by a variety of HP host applications. The following applications are supported through WRQTICL: - HP AdvanceMail - HP Information Access - HP NewWave Mail - HP NewWave Access - HP LaserRX NetBIOS The Reflection Network Series for DOS TCP/IP stack can be used with a NetBIOS interface to provide the transport layer for PC LANs such as LAN Manager. Many TCP/IP applications are compatible with WRQ's TCP/IP through the interfaces listed above. The following vendors have certified the use of WRQ's TCP Connection with their applications (current as of November 1993): 1 AGE Logic 14 Microsoft Corp. 2 Binary Research 15 Network Computing Devices 3 Cognos 16 Open Connect Systems 4 Computer Assoc. Inernational 17 Persoft 5 DCA 18 Pilot Software 6 DEC 19 Quarterdeck Office Systems 7 Diversified Computer Systems 20 Scopus 8 FTG Data Systems 21 SyBase 9 HP 22 Techgnosis 10 Hummingbird Communications 23 Visionware 11 JSB 24 VMark Software 12 Micro Data Base Systems 25 White Pine Software 13 Micro Decisionware Please note that this listing is incomplete, as several other companies have agreed to test their applications with WRQ's TCP/IP. Also, Windows Sockets compliance will soon provide compatibility with an even wider range of applications. If you are not sure if your application is compatible with Reflection Network Series, please contact WRQ. 5. CAN REFLECTION FOR DOS TERMINAL EMULATORS USE MY TCP/IP SOFTWARE? To use Telnet or FTP with Reflection for DOS 4.2 or later, you need a "telnet manager" interface module. If your TCP/IP is WRQ's Reflection Network Series for DOS TCP Connection or 3000 Connection, then this module is included. If you have a third-party TCP/IP stack listed below, the Reflection Network Series Telnet Connection provides the appropriate "telnet manager" module. 3Com TCP with Demand Protocol Architecture Beame & Whiteside BWNFS DEC PATHWORKS for DOS TCP/IP, version 4.x FTP PC/TCP Hewlett-Packard ARPA Services, version 2.0 and higher Microsoft LAN Manager TCP/IP, version 2.10 and higher Novell LAN Workplace for DOS, version 4.0 and higher Sun Microsystems PC-NFS (with or without NIS) Ungermann-Bass Net/One for DOS Wollongong PathWay for DOS 6. CAN REFLECTION FOR WINDOWS EMULATORS USE MY TCP/IP SOFTWARE? To use Telnet in Reflection for Windows emulators version 3.7 through 4.01, you need Reflection Network Series for DOS (TCP Connection, 3000 Connection, or Telnet Connection) as explained in 5. above. Reflection for Windows 4.1 or later is also Windows Sockets compatible. If you use a TCP/IP stack that has a WINSOCK.DLL file (see 3. above), the connection type TELNET-MGR will automatically use it. The following table summarizes Reflection for Windows emulator Telnet support: RnWin RnWin versions 3.7 version 4.1 through 4.01 or later Reflection Network Series YES YES TCP Connection Reflection Network Series YES YES 3000 Connection Third-party TCP/IP using YES YES Reflection Network Series Telnet Connection Windows Sockets compliant no YES TCP/IP stacks 7. CAN REFLECTION X USE MY TCP/IP STACK? Reflection X is WRQ's PC-based X Window System server. Reflection X is Windows Sockets compatible, so it can work with Windows Sockets TCP/IP stacks such as those listed in 3. above. In addition, Reflection X works with the following TCP/IP stacks (via the Virtual Socket Library): Reflection Network Series for DOS version 2.02 and later. (TCP Connection is included in the Reflection X Connectivity Suite.) 3Com 3+Open TCP Beame & Whiteside TCP/IP, 2.2 or later Digital PATHWORKS for DOS TCP/IP, 4.0 or later FTP PC/TCP, 2.05 or later HP ARPA Services for DOS, 2.1 or later Microsoft LAN Manager TCP/IP, 2.1 or later Novell LAN WorkPlace for DOS, 4.01 or later Sun Microsystems PC-NFS, 3.01 and later Ungermann-Bass Net/One, 16.4 or later 8. CAN REFLECTION FTP FOR WINDOWS USE MY TCP/IP STACK? Reflection FTP for Windows is bundled with Reflection for Windows emulators (version 4.1 and later) and Reflection X (version 4.0 and later). It can use the same TCP/IP interface as the product it is bundled with (see 5., 6., 7. above). This includes third-party Windows Sockets compliant stacks. 9. CAN NS/VT (VT-MGR CONNECTIONS) RUN OVER A WINSOCK.DLL? HP 3000 NS/VT connectivity over Windows Sockets compliant TCP/IP products will be part of the Reflection Network Series for Windows 3000 Connection and NS Open packages (scheduled beta release April 1994). The 3000 Connection includes WRQ's TCP/IP for Windows. The NS Open package does not include TCP/IP; it is geared for using the NS/VT over a third-party Windows Sockets compliant TCP/IP. However, because of non-standard characteristics of the HP protocols (TCP differences; name resolution uses Probe; etc.), not all third-party Windows Sockets compliant TCP/IP stacks may work with NS Open. The only way we can certify that NS Open is compatible with a vendor's TCP/IP is through an empirical testing and certification process. Testing is currently planned for the following Windows Sockets compliant stacks: - Reflection Network Series for DOS 2.2 (TCP Connection, NS Connection, or 3000 Connection) - Reflection Network Series for Windows (TCP Connection or 3000 Connection). The 3000 Connection will include the NS Open module. - Microsoft Windows NT - IBM TCP/IP 2.0 for OS/2 with DOS/Windows Access Kit - other third party TCP/IP stacks (to be announced) Also, to use NS Open with some Winsock TCP/IP stacks, the HP 3000 may need to support stream mode VT operation, which requires patches from HP for the MPE/iX or MPE/V host operating system. MPE/iX Release 5.0 will support stream mode without any need for patches. The WRQ proprietary file transfer protocol will not immediately support Fast File Transfer mode (FFT) over Windows Sockets. A future release of Reflection for Windows is planned to add this ability and other enhancements that may be needed for NS Open in some environments. 10. HOW DO ALL THESE NETWORK MODULES FIT TOGETHER? Here's a diagram of WRQ Reflection Network Series for DOS architecture (version 2.01 or later; version 2.2 for Windows Sockets): ============ ============== ============ +.......+ +............+ +.........+ !Reflection! ! RWin ! ! RWin ! : : : : : : !for DOS or! ! 4.1 ! ! 4.1 ! : : : : : : ! Windows ! !(TELNET-MGR)! ! (VT-MGR) ! :Windows: :TCP/HP ARPA : : NetIPC : ! Ver 4.XX ! ============== ============ :Sockets: :Socket Appl : : Appl : ! (VT-MGR ! ============== ************ :Compat-: : : : : ! -or- ! ! ! * * : ible : : : : : !TELNET-MGR! !RNTELNET.DLL! *RNNSVT.DLL* : Appl : : : : : !Connection! ! (RWin 4.1) ! *(NS Open) * : : : : : : ! Type) ! ! ! * * : : : : : : ============ ============== ************ +.......+ +............+ +.........+ +----------+ +-----------------------------------+ +------------+ +---------+ | | | WINSOCK.DLL | |WSOCKETS.DLL| | | |CONMGR.EXE| | Windows Sockets interface | | -or- | |W3IPC.DLL| | | | for WRQ RNS DOS 2.2 | |WIN_SOCK.DLL| | | +----------+ +-----------------------------------+ +------------+ +---------+ +----------+ +--------------------------------------------------+ +---------+ |VTMGR.EXE | | | | | | -or- | | WRQHPSO.EXE | | WRQTICL | |TELMGR.EXE| | | | | +----------+ +--------------------------------------------------+ +---------+ +---------------------------------------------------------------------------+ | WRQTCP.EXE | +---------------------------------------------------------------------------+ +---------------------------------------------------------------------------+ | TCP2PDIS.EXE | +---------------------------------------------------------------------------+ +---------------------------------------------------------------------------+ | RODI.EXE -or- RNDIS.EXE | +---------------------------------------------------------------------------+ +---------------------------------------------------------------------------+ | ODI -or- NDIS card driver | +---------------------------------------------------------------------------+ Key: +--+ RNS ==== Reflection +..+ Non-WRQ **** RNS for | | for DOS ! ! 1/2/4/7 : : network * * Windows +--+ module ==== Emulator +..+ application **** module This document is available as technote #8016 from: Bulletin Board System: telnet bbs.wrq.com, or 206-217-0145 (file area 2) Anonymous FTP server: ftp anon.wrq.com (directory /bbsfiles/technotes) Technotes By Fax request line (24 hours): 206-217-9575 CompuServe: GO REFLECTION or GO WRQFORUM -- Walker Richer & Quinn, Inc. Tech Support: 206-217-7000 (voice) Technical Support support@wrq.com (email) 2815 Eastlake Ave. East GO REFLECTION (CompuServe) Seattle, WA 98102 206-217-9492 (fax) 206-217-0145 (BBS, V.32bis) bbs.wrq.com (BBS, telnet) 
